Manage event with content on calendar with timeline

ABSTRACT

Management of an event with a content on a calendar with a timeline is provided. An application such as a calendar application detects a selection of the event with the content on the calendar. A context menu is displayed on the calendar, where the context menu includes an add control. An activation of the add control is detected. The event with the content is duplicated on the timeline of the calendar.

RELATED APPLICATIONS

This applications claims the benefit of U.S. Provisional Patent Application Ser. No. 62/015,350 filed on Jun. 20, 2014. The disclosure of the provisional application is incorporated herein in its entirety.

BACKGROUND

Legacy calendar views in scheduling applications provide limited information. Alternatively, the legacy calendar views in scheduling applications provide excessive information. Legacy calendar views are usually used in detailed configurations for daily and weekly actions. However, users are underserved in long term synapsis of associated actions in legacy calendar views. Addition of actions and other items into legacy calendar views prove challenging for long term synapsis of associated actions.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to exclusively identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Embodiments are directed to managing an event with a content on a calendar with a timeline. In some example embodiments, a calendar application may detect a selection of an event with a content on a calendar. A context menu may be displayed on the calendar, where the context menu includes an add control. An activation of the add control may be detected. The event with the content may be duplicated on a timeline of the calendar.

These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory and do not restrict aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram illustrating an example of managing an event with a content on a calendar with a timeline, according to embodiments;

FIG. 2 illustrates an example of adding an event with a content to a timeline, according to embodiments;

FIG. 3 illustrates an example of removing an event with a content from a timeline, according to embodiments;

FIG. 4 illustrates another example of removing an event with a content from a timeline, according to embodiments;

FIG. 5 is a simplified networked environment, where a system according to embodiments may be implemented;

FIG. 6 illustrates a general purpose computing device, which may be configured to manage an event with a content on a calendar with a timeline; and

FIG. 7 illustrates a logic flow diagram for a process to manage an event with a content on a calendar with a timeline, according to embodiments.

DETAILED DESCRIPTION

As briefly described above, an event with a content may be managed on a calendar with a timeline by a calendar application. The calendar application may detect a selection of an event with a content on a calendar. A context menu may be displayed on the calendar, where the context menu includes an add control. An activation of the add control may be detected. The event with the content may be duplicated on a timeline of the calendar.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.

While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computing device, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es). The computer-readable storage medium is a computer-readable memory device. The computer-readable memory device includes a hardware device that includes a hard disk drive, a solid state drive, a compact disk, a memory chip, among others. The computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, and a flash drive.

Throughout this specification, the term “platform” may be a combination of software and hardware components to manage an event with a content on a calendar with a timeline. Examples of platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems. The term “server” generally refers to a computing device executing one or more software programs typically in a networked environment. However, a server may also be implemented as a virtual server (software programs) executed on one or more computing devices viewed as a server on the network. More detail on these technologies and example embodiments may be found in the following description.

FIG. 1 is a conceptual diagram illustrating an example of managing an event with a content on a calendar with a timeline, according to embodiments.

In a diagram 100, a computing device 104 may execute a calendar application 102. The computing device may include a tablet device, a laptop computer, a desktop computer, a smart phone, among others. The computing device 104 may display the calendar application 102 to a user 106. The user 106 may be allowed to interact with the calendar application 102 through an input device or touch enabled display component of the computing device 104. The user 106 may interact with the calendar application 102 with a keyboard based input, a mouse based input, a voice based input, a pen based input, a gesture based input, among others. The gesture based input may include one or more touch based actions such as a touch action, a swipe action, a combination of each, among others.

The calendar application 102 may include a timeline 120 as a component placed adjacent to and below a calendar. The timeline 120 may also be presented as a stand-alone component. The timeline 120 may include a linear presentation of events during a time period divided based on a time unit such as a day. Events presented on the timeline may be duplicates of the events on the calendar displayed by the calendar application 102. A user 106 may be allowed to interact with the calendar and the timeline 120 to manage an event with a content. The event with the content may be displayed on the calendar and duplicated on the timeline 120.

While the example system in FIG. 1 has been described with specific components including the computing device 104, the calendar application 102, the timeline 120, embodiments are not limited to these components or system configurations and can be implemented with other system configuration employing fewer or additional components.

FIG. 2 illustrates an example of adding an event with a content on a timeline, according to embodiments.

In a diagram 200, a calendar application 202 that displays a calendar 226 used to add an event with a content to a timeline 220 may be described. The calendar application 202 may provide one or more components to manage the calendar 226 and the timeline 220. A date picker component 204 may allow a user to select a date from a displayed range. The selected date may be displayed in the calendar 226 that shows the date within a date range that is configurable. The date range of the calendar 226 may include a day, a week, a month, a year, among others. A current date range may be illustrated with a date range label 208. The date range may also be partitioned vertically based on a time unit such as a day 210. The time units may be scrollable. The calendar 222 may also be partitioned horizontally based on an hour based unit 212. The hour based units may be scrollable. An “all day” unit may persist on a top section of the calendar 226 to show one or more events that last during a time unit such as a day.

The calendar 222 may also be selectable through a calendar selection control 206. The calendar application 202 may display one or more calendars that may be selectable through the calendar selection control 206 and other calendar selection controls displayed adjacent to the calendar selection control 206.

The timeline 220 may be displayed stand-alone or in conjunction with a calendar. The events displayed in the timeline 220 may be duplicates of events stored in the calendar 226. In addition, the timeline 220 may display a date range of events that may be scrollable through a scroll control 224. The date range may be presented with a date range label 222. The date range may be partitioned based on time units such as an hour, a day 228, a week, a month, a year, among others. The date range may be selectable based on a selection of the range by a user through a range selection control such as “weekly,” among others.

The calendar application 202 may display an event 214 with a content 215 on the calendar 226. The content 215 may be stored in the event 214. Alternatively, the content 215 may be presented as a link on the event 214 to a local or external storage that stores the content 215. The content 215 may include an audio file, a video file, an image file, a document, among others.

The calendar application 202 may detect a selection on the event 214 on the calendar 226. The selection may include a mouse based input such as a click event, a touch based input such as tap action, among others. In response to the selection of the event 214, a context menu 216 may be displayed. The context menu 216 may be displayed in a location that is in proximity to, adjacent to, or superimposed on the event 214. The context menu 216 may include one or more controls to manage the event 214 with the content 215. One of the controls may include an add control. The add control may execute operations to add the event 214 to the timeline 220 as a duplicate.

In response to detecting an activation 218 of the add control, the event 214 with the content 215 may be duplicated on the timeline 220. The event 214 may be added to a date on the timeline 220 that corresponds to a date of the event 214. The content 215 may be included in the event 214 during the duplication operations to add the event 214 to the timeline 220. The timeline may be scrolled to a date range that includes a date of the event 214. The duplicate of the event 214 with the content 215 may be displayed on the date on the timeline 220. Alternatively, a link to the content 215 may be inserted into the event on the timeline that is a duplicate of the event 214. The link may be presented as the content 215 in the event on the timeline 220.

A current date may also be highlighted on the timeline. The current date may be highlighted in response to detecting that the current date is within a date range that includes the event with the content on the timeline. In addition, the event with the content may be highlighted on the timeline 220 through an animation. The event may be highlighted with an animation to emphasize a completion of the duplication of the event 214 with the content 215 on the timeline 220. The animation may include a blinking animation applied to the event, a rotating animation applied to the event, a fade in animation applied to the event, or an animated object that encompasses the event with the content on the timeline 220.

FIG. 3 illustrates an example of removing an event with a content from a timeline, according to embodiments.

In a diagram 300, a calendar application 302 may display an event 314 with a content on a calendar 326 that is duplicated as an event 304 with a content on a timeline 320. The calendar application 302 may detect a selection of the event 304 with the content. The selection may include a mouse based input such as a click event, a touch based input such as tap action, among others. In response to the selection, the calendar application 302 may display a context menu 316. The context menu 316 may be displayed in a location that is in proximity to, adjacent to, superimposed on the event 304 with the content. The context menu 316 may include a delete control that executes operations to remove the selected event 304 with the content from the timeline 320.

In response to detecting an activation 318 of the delete control, the calendar application 302 may remove the event 304 with the content from the timeline 320. The event 314 with the content on the calendar, that is a duplicate of the event 304 with the content, may not be removed without further input. The calendar 326 may be scrolled to a date range that includes a date of the event 304 that corresponds to a date of the event 314. The event 314 with the content may be displayed on the calendar 326.

FIG. 4 illustrates another example of removing an event with a content from a timeline, according to embodiments.

In a diagram 400, a calendar application 402 may display an event 414 with a content on a calendar 426. A duplicate of the event 414 with the content may be displayed on a timeline 420 as an event 404 with a content. The calendar application 402 may detect a selection on the event 414 with the content on the calendar 426. In response to detecting the selection and the event 404 as a duplicate of the event 414, a context menu 416 may be displayed with a delete control. The context menu 416 may be displayed in a location that is in proximity to, adjacent to, or superimposed on the event 414 with the content on the calendar 426. In response to detecting an activation 418 of the delete control, the event 404 with the content on the timeline 420 may be removed from the timeline 420.

The calendar application 402 may detect another selection on the content of the event 414 on the calendar 426. A display component that includes a local component of the calendar application 402 or an external application may be initiated to display the content in the event 414. The content in the event 414 may be provided to the display component to display the content.

The technical advantage of managing an event with a content on a calendar with a timeline may be improved usability and enhanced reliability of display devices in an event with a content addition, removal, and management, among other features compared to static event presentation based solutions.

The example scenarios and schemas in FIG. 1 through 4 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Managing an event with a content on a calendar with a timeline may be implemented in configurations employing fewer or additional components in applications and user interfaces. Furthermore, the example schema and components shown in FIG. 1 through 4 and their subcomponents may be implemented in a similar manner with other values using the principles described herein.

FIG. 5 is an example networked environment, where embodiments may be implemented. A calendar application configured to manage an event with a content on a calendar with a timeline may be implemented via software executed over one or more servers 514 such as a hosted service. The platform may communicate with client applications on individual computing devices such as a smart phone 513, a laptop computer 512, or desktop computer 511 (‘client devices’) through network(s) 510.

Client applications executed on any of the client devices 511-513 may facilitate communications via application(s) executed by servers 514, or on individual server 516. A calendar application may display a context menu with an add control on a calendar to add an event with a content on the calendar to a timeline. The event with the content on the calendar may be duplicated as an event with a content on the timeline, in response to an activation of the add control. The calendar application may store data associated with the calendar and the timeline in data store(s) 519 directly or through database server 518.

Network(s) 510 may comprise any topology of servers, clients, Internet service providers, and communication media. A system according to embodiments may have a static or dynamic topology. Network(s) 510 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 510 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 510 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 510 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 510 may include wireless media such as acoustic, RF, infrared and other wireless media.

Many other configurations of computing devices, applications, data sources, and data distribution systems may be employed to manage an event with a content on a calendar with a timeline. Furthermore, the networked environments discussed in FIG. 5 are for illustration purposes only. Embodiments are not limited to the example applications, modules, or processes.

FIG. 6 illustrates a general purpose computing device, which may be configured to manage an event with a content on a calendar with a timeline, arranged in accordance with at least some embodiments described herein.

For example, the computing device 600 may be used to manage an event with a content on a calendar with a timeline. In an example of a basic configuration 602, the computing device 600 may include one or more processors 604 and a system memory 606. A memory bus 608 may be used for communication between the processor 604 and the system memory 606. The basic configuration 602 may be illustrated in FIG. 6 by those components within the inner dashed line.

Depending on the desired configuration, the processor 604 may be of any type, including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. The processor 604 may include one more levels of caching, such as a level cache memory 612, a processor core 614, and registers 616. The processor core 614 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof. A memory controller 618 may also be used with the processor 604, or in some implementations, the memory controller 618 may be an internal part of the processor 604.

Depending on the desired configuration, the system memory 606 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The system memory 606 may include an operating system 620, a calendar application 622, and a program data 624. The calendar application 622 may display a context menu with an add control on a calendar to add an event with a content on the calendar to a timeline. The event with the content on the calendar may be duplicated as an event with a content on the timeline, in response to an activation of the add control. Components of the calendar application 622 (such as a user interface) may also be displayed on a display device associated with the computing device 600. An example of the display device may include a hardware screen that may be communicatively coupled to the computing device 600. The display device may include a touch based device that detects gestures such as a touch action. The display device may also provide feedback in response to detected gestures (or any other form of input) by transforming one or more user interfaces of the calendar application 622 such as the calendar and the timeline, displayed by the touch based device. The program data 624 may include, among other data, a timeline data 628, or the like, as described herein. The timeline data 628 may include the event with a content, subject name of the event with a content, among others.

The computing device 600 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 602 and any desired devices and interfaces. For example, a bus/interface controller 630 may be used to facilitate communications between the basic configuration 602 and one or more data storage devices 632 via a storage interface bus 634. The data storage devices 632 may be one or more removable storage devices 636, one or more non-removable storage devices 638, or a combination thereof. Examples of the removable storage and the non-removable storage devices may include magnetic disk devices, such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives, to name a few. Example computer storage media may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data.

The system memory 606, the removable storage devices 636, and the non-removable storage devices 638 may be examples of computer storage media. Computer storage media may include, but may not be limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the computing device 600. Any such computer storage media may be part of the computing device 600.

The computing device 600 may also include an interface bus 640 for facilitating communication from various interface devices (for example, one or more output devices 642, one or more peripheral interfaces 644, and one or more communication devices 666) to the basic configuration 602 via the bus/interface controller 630. Some of the example output devices 642 may include a graphics processing unit 648 and an audio processing unit 650, which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 652. One or more example peripheral interfaces 644 may include a serial interface controller 654 or a parallel interface controller 656, which may be configured to communicate with external devices, such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 658. An example communication device 666 may include a network controller 660, which may be arranged to facilitate communications with one or more other computing devices 662 over a network communication link via one or more communication ports 664. The one or more other computing devices 662 may include servers, client equipment, and comparable devices.

The network communication link may be one example of a communication media. Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of the modulated data signal characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media. The term computer-readable media, as used herein, may include both storage media and communication media.

The computing device 600 may be implemented as a part of a general purpose or specialized server, mainframe, or similar computer, which includes any of the above functions. The computing device 600 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.

Example embodiments may also include managing an event with a content on a calendar with a timeline. These methods may be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, using devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be co-located with each other, but each may be with a machine that performs a portion of the program. In other examples, the human interaction may be automated such as by pre-selected criteria that may be machine automated.

FIG. 7 illustrates a logic flow diagram for a process to manage an event with a content on a calendar with a timeline, according to embodiments. Process 700 may be implemented on a calendar application.

Process 700 begins with operation 710, where a selection of an event with an content may be detected on the calendar. At operation 720, a context menu may be displayed on the calendar, where the context menu includes an add control. An activation of the add control may be detected at operation 730. At operation 740, the event with the content may be duplicated on the timeline of the calendar.

The operations included in process 700 are for illustration purposes. A calendar application according to embodiments may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.

According to some examples, a method that is executed on a computing device to manage an event with a content on a calendar with a timeline may be described. The method may include detecting a selection of the event with the content on the calendar, displaying a context menu on the calendar, where the context menu includes an add control, detecting an activation of the add control, and duplicating the event with the content on the timeline of the calendar.

According to other examples, the method may further include displaying the context menu in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar. The timeline may be scrolled to a date range that includes a date of the event with the content on the calendar and the event with the content may be displayed within the date on the timeline. A current date may be highlighted on the timeline, in response to detecting that the current date is within a date range that includes a date of the event with the content on the timeline. The event with the content may be highlighted on the timeline through an animation that includes one from a set of: a blinking animation applied to the event, a rotating animation applied to the event, a fade in animation applied to the event, and an animated object that encompasses the event.

According to further examples, the method may further include detecting the content to include one or more from a set of: an audio file, a video file, an image file, and a document and duplicating the event with the content on the calendar by creating the event with the content on the timeline with a link to the content stored in the event on the calendar. The method may further include detecting a second selection of the event with the content on the timeline, displaying another context menu on the timeline, where the context menu includes a delete control, detecting an activation of the delete control, and removing the event with the content from the timeline. The other context menu may be displayed in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the timeline. The method may further include scrolling to a date range on the calendar that includes a date of the event with the content on the timeline and displaying the event with the content within the date on the calendar.

According to some examples, a computing device to manage an event with a content on a calendar with a timeline may be described. The computing device may include a display device, a memory, a processor coupled to the memory and the display device. The processor may be configured to execute a calendar application in conjunction with instructions stored in the memory. The calendar application may be configured to detect a selection of the event with the content on the calendar, display a context menu on the calendar in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar, on the display device, where the context menu includes an add control, detect an activation of the add control, and duplicate the event with the content on the timeline of the calendar, on the display device.

According to other examples, the calendar application is further configured to detect the event with the content on the calendar as duplicated in the event with the content on the timeline, detect a second selection of the event with the content on the calendar, display another context menu on the calendar, where the context menu includes a delete control, detect an activation of the delete control, and remove the event with the content from the timeline. The other context menu may be displayed in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar, on the display device. The calendar application is further configured to scroll to a date range on the timeline that includes a date of the event with the content on the calendar. The calendar application is further configured to detect a second selection on the content of the event on the calendar, initiate a display component that includes one from a set of: a local component and an external application to display the content, and provide the content to the display component to display the content.

According to some examples, a computer-readable memory device with instructions stored thereon to manage an event with a content on a calendar with a timeline may be described. The instructions may include actions that are similar to the method described above.

According to some examples, a means to manage an event with a content on a calendar with a timeline may be described. The means to manage an event with a content on a calendar with a timeline may include a means for detecting a selection of the event with the content on the calendar, a means for displaying a context menu on the calendar, where the context menu includes an add control, a means for detecting an activation of the add control, and a means for duplicating the event with the content on the timeline of the calendar.

The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments. 

What is claimed is:
 1. A method executed on a computing device to manage an event with a content on a calendar with a timeline, the method comprising: detecting a selection of the event with the content on the calendar; displaying a context menu on the calendar, wherein the context menu includes an add control; detecting an activation of the add control; and duplicating the event with the content on the timeline of the calendar.
 2. The method of claim 1, further comprising: displaying the context menu in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar.
 3. The method of claim 1, further comprising: scrolling the timeline to a date range that includes a date of the event with the content on the calendar; and displaying the event with the content within the date on the timeline.
 4. The method of claim 1, further comprising: highlighting a current date on the timeline, in response to detecting that the current date is within a date range that includes a date of the event with the content on the timeline.
 5. The method of claim 1, further comprising: highlighting the event with the content on the timeline through an animation that includes one from a set of: a blinking animation applied to the event, a rotating animation applied to the event, a fade in animation applied to the event, and an animated object that encompasses the event.
 6. The method of claim 1, further comprising: detecting the content to include one or more from a set of: an audio file, a video file, an image file, and a document; and duplicating the event with the content on the calendar by creating the event with the content on the timeline with a link to the content stored in the event on the calendar.
 7. The method of claim 1, further comprising: detecting a second selection of the event with the content on the timeline; and displaying another context menu on the timeline, wherein the context menu includes a delete control.
 8. The method of claim 7, further comprising: detecting an activation of the delete control; and removing the event with the content from the timeline.
 9. The method of claim 7, further comprising: displaying the other context menu in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the timeline.
 10. The method of claim 7, further comprising: scrolling to a date range on the calendar that includes a date of the event with the content on the timeline.
 11. The method of claim 10, further comprising: displaying the event with the content within the date on the calendar.
 12. A computing device to manage an event with a content on a calendar with a timeline, the computing device comprising: a display device; a memory; a processor coupled to the memory and the display device, the processor executing a calendar application in conjunction with instructions stored in the memory, wherein the calendar application is configured to: detect a selection of the event with the content on the calendar; display a context menu on the calendar in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar, on the display device, wherein the context menu includes an add control; detect an activation of the add control; and duplicate the event with the content on the timeline of the calendar, on the display device.
 13. The computing device of claim 12, wherein the calendar application is further configured to: detect the event with the content on the calendar as duplicated in the event with the content on the timeline; detect a second selection of the event with the content on the calendar; and display another context menu on the calendar, wherein the context menu includes a delete control.
 14. The computing device of claim 13, wherein the calendar application is further configured to: detect an activation of the delete control; and remove the event with the content from the timeline.
 15. The computing device of claim 13, wherein the calendar application is further configured to: display the other context menu in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar, on the display device.
 16. The computing device of claim 13, wherein the calendar application is further configured to: scroll to a date range on the timeline that includes a date of the event with the content on the calendar.
 17. The computing device of claim 12, wherein the calendar application is further configured to: detect a second selection on the content of the event on the calendar; initiate a display component that includes one from a set of: a local component and an external application to display the content; and provide the content to the display component to display the content.
 18. A computer-readable memory device with instructions stored thereon to manage an event with a content on a calendar with a timeline, the instructions comprising: detecting a selection of the event with the content on the calendar; displaying a context menu on the calendar in a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event with the content on the calendar, wherein the context menu includes an add control; detecting an activation of the add control; and duplicating the event with the content on the timeline of the calendar.
 19. The computer-readable memory device of claim 18, wherein the instructions further comprise: detecting a second selection of the event with the content on the timeline; displaying another context menu on the timeline, wherein the context menu includes a delete control; detecting an activation of the delete control; and removing the event with the content from the timeline.
 20. The computer-readable memory device of claim 18, wherein the instructions further comprise: detecting the event with the content on the calendar as duplicated in the event with the content on the timeline; detecting a second selection of the event with the content on the calendar; displaying another context menu on the calendar, wherein the context menu includes a delete control; and scrolling to a date range on the timeline that includes a date of the event with the content on the calendar. 